Skip to main content

HTMLTextBox How To's

How to's for the HTMLTextBox guide.

How to Use HTMLTextBox?​

How to Use HTMLTextBox?​

Follow the steps below to add and configure the HTMLTextBox component on a form.

1. Adding the HTMLTextBox Component to a Form​

  1. Open the relevant Form screen in the development interface.
  2. Go to the Toolbox panel on the left.
  3. Locate the HTMLTextBox component.
  4. Drag and drop the component onto the form.

2. Viewing Properties​

When the component is selected, the Property Viewer panel opens on the right.

This panel contains the following main tabs:

  • General
  • Label
  • Behavior
  • Appearance
  • Events

All configuration settings of the component can be managed from these tabs.

3. Configuring General Settings​

In the General tab, the following settings are typically configured:

  • Field name (Name)
  • Default content
  • Whether the field is required
  • Visibility and accessibility settings

These options define how the HTMLTextBox behaves on the form.

4. Using Rich Text Features​

When the form is running, the user can:

  • Format text (bold, italic, lists, etc.)
  • Add headings or paragraphs
  • Insert links or images
  • Visually edit the content

The entered content is stored in HTML format in the background.

5. Using Events (Optional)​

By using the Events tab, you can:

  • Trigger actions when the content changes
  • Apply validation rules
  • Enable interaction with other form components

Example Usage Scenario​

Scenario:
A request form requires the user to enter a detailed description.

Solution:

  • Add an HTMLTextBox to the form
  • The user enters and formats the description
  • The description is saved as HTML and displayed in reports

Tips​

  • Prefer HTMLTextBox instead of TextBox for long and formatted text.
  • HTMLTextBox is more suitable when visual content is required.
  • Avoid unnecessary use for very short and simple text inputs.

What Is HTMLTextBox?​

What Is HTMLTextBox?​

HTMLTextBox is a form component used to create and edit rich text content on a form.
It allows users to visually format text without requiring any HTML knowledge.

This component works with the What You See Is What You Get (WYSIWYG) approach, meaning the content users see on the screen is saved exactly the same way as HTML.

What Is It Used For?​

HTMLTextBox is commonly preferred in the following scenarios:

  • Entering descriptions, explanatory notes, or detailed text
  • Creating richly formatted content (bold, italic, lists, links, etc.)
  • Providing text areas that include images or hyperlinks
  • Preparing email templates, announcement texts, or descriptive fields

Key Features​

  • Rich Text Editing
    Supports bold, italic, underline, headings, and lists.

  • HTML Output
    The entered content is stored in HTML format and can be reused elsewhere.

  • Image and Link Support
    Images and hyperlinks can be inserted into the text.

  • User-Friendly Interface
    Even users without HTML knowledge can easily create content.

Where Can It Be Used?​

  • Form descriptions
  • Request / process descriptions
  • Informational texts displayed to users
  • Report or output contents

Notes​

  • HTMLTextBox is client-side and runs in the browser.
  • Since the generated content is HTML, it can be displayed consistently across different screens.
  • It is suitable for all forms that require long and formatted text input.

How to Use Client Enabled?​

What is Client Enabled?​

Client Enabled is a property that defines whether a form control is active (enabled) on the client side when the form is first loaded.
If it is set to True, the control is immediately usable by the user.
If it is set to False, the control is disabled and cannot be interacted with until a specific condition or rule activates it.

This property is especially useful for controlling the user’s interaction flow and applying dynamic behaviors using the Rule Manager.

What Does It Do?​

The property allows developers to:

  • Control when a form control becomes interactive.
  • Prevent users from entering or changing data until prerequisites are met.
  • Dynamically enable or disable controls based on user input or logic.

Example Scenario — Conditional Activation​

Scenario:
A form contains a checkbox called “I Accept Terms” and a text field called “Signature.”
The goal is to make the “Signature” field inactive until the user checks “I Accept Terms.”

Steps to Implement:​

  1. Select the “Signature” field in the form editor.

  2. In the Properties panel, find the Client Enabled field.

  3. Set the value to False — the field will now be disabled by default when the form loads.

  4. Open the Rule Manager.

  5. Add a new rule:

    Condition:

Action:

  1. Save and publish the form.

Result:​

  • When the form loads, the “Signature” field is disabled.
  • Once the user checks “I Accept Terms,” the field automatically becomes active and editable.

Behavior Summary​

Property StateDescription
TrueThe control is active and ready for user interaction when the form loads.
FalseThe control is disabled at load time and can be enabled dynamically via rules or code.

Notes & Best Practices​

  • Use the Client Enabled property to manage client-side interactivity without requiring server actions.
  • Combine it with Rule Manager to define when and how controls become active.
  • Remember: if server enablement is disabled, the client cannot enable the control even if Client Enabled is set to True.
  • By default, this property is set to True (active).

Summary​

Client Enabled improves form usability by letting developers control when and how users interact with form controls.
It is essential for creating responsive, condition-based form experiences where user actions dynamically change the form’s state.